update changelog for releasing v1.8.1 (#1576) #1577
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
### Description go-sql-driver#1559 and go-sql-driver#1567 are fixed. Let's release a new version v1.8.1. ### Checklist - [x] Code compiles correctly - [x] Created tests which fail without the change (if possible) - [x] All tests passing - [x] Extended the README / documentation, if necessary - [x] Added myself / the copyright holder to the AUTHORS file <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **Bug Fixes** - Addressed race condition issues for enhanced stability. - **New Features** - Improved database compatibility with charset and collation adjustments. - Enhanced security and flexibility through the introduction of new configuration options. - **Major Changes** - Dropped support for older versions of Go (1.13-1.17) to leverage newer language features. - Improved number parsing for efficiency and accuracy. - Added configurable logging per connection for better diagnostics. - **Enhancements** - Fixed issues with ColumnType.DatabaseTypeName to improve data handling. - Introduced connection attributes for more detailed connection information. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
WalkthroughThe recent updates focus on enhancing stability and compatibility. Version 1.8.1 brings crucial bugfixes to address race conditions related to context cancellation. Meanwhile, version 1.8.0 introduces significant changes, such as improved database character set support, dropping older Go versions, and new functional options for better configuration. Additionally, other updates include a more versatile logger, corrected data type naming for Changes
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Review Status
Actionable comments generated: 0
Configuration used: CodeRabbit UI
Files selected for processing (1)
- CHANGELOG.md (1 hunks)
Additional comments: 3
CHANGELOG.md (3)
- 1-42: The changelog is well-structured and provides a clear overview of changes across versions. However, consider the following formatting improvements for consistency and clarity:
- Ensure consistent use of spaces after hyphens in lists.
- Verify the correctness of all external links to pull requests to ensure they are accessible.
- Attribute contributions consistently, starting with an uppercase letter after the hyphen for each list item.
- 5-5: The documentation of the race condition fix in PRs fix race condition when context is canceled #1562 and Fix issue 1567 #1570 under version 1.8.1 accurately reflects the collective effort to address this issue, as noted in the provided learning. This clear attribution helps users understand the context and significance of the changes.
- 1-42: While reviewing the changelog, ensure that all technical terms and references are used correctly, and consider rephrasing for clarity if necessary. However, be cautious of false positives from automated tools, especially regarding technical content and code references, which may not apply to the structured and technical nature of a changelog.
methane
approved these changes
Apr 28, 2024
methane
pushed a commit
to methane/mysql
that referenced
this pull request
Apr 30, 2024
…iver#1577) cherry pick of shogo82148@476df92 <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **Bug Fixes** - Addressed race conditions when the context is canceled. - **New Features** - Enhanced database connection with charset and collation settings. - Improved path escaping in database names. - Dropped support for Go versions 1.13-17. - Implemented parsing numbers over text protocol. - Introduced new configuration options for advanced usage. - **Enhancements** - Made logger configurable per connection. - Fixed handling of `mediumint unsigned` in `ColumnType.DatabaseTypeName`. - Added connection attributes for more detailed connection information. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
cherry pick of shogo82148@476df92
Summary by CodeRabbit
mediumint unsignedinColumnType.DatabaseTypeName.